-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add multiple listeners for Virtual Nodes, Routers, and Gateways #27368
Conversation
Community NoteVoting for Prioritization
For Submitters
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome @benmurden 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
"spec.0.listener.0.connection_pool.0.http", | ||
"spec.0.listener.0.connection_pool.0.http2", | ||
"spec.0.listener.0.connection_pool.0.tcp", | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are no longer singleton items, so this would throw an error. Not sure of a way to keep these checks while adding the ability to specify multiple listeners. Advice welcome here.
ExactlyOneOf: file configuration
block reference (spec.0.listener.0.connection_pool.0.grpc) can only
be used with TypeList and MaxItems: 1 configuration blocks
Thank you for your contribution! 🚀 Please note that the Remove any changes to the |
Wouldn't we also need to enable specifying port match in route and gateway route? AWS throws errors if you attempt to create routes to gateways/routers/nodes with multiple listeners without those specifications. |
@SW386 Thanks for the comment. Do you have an example of a config that would now fail as a result of these changes? |
I do not have anything I can share, but If you go to the AWS Appmesh console and have a route defined without a port match connected to a node, then try to modify that node to add multiple listeners, you will receive |
I see, thanks for clarifying. Are there examples of Terraform resources that validate based on the content of other resources? It seems to me this sort of thing is usually covered by documentation e.g. Security Groups and Security Group Rules https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule. |
I don't have anything on the Terraform side since those resources are not updated to include port match and multiple listeners are not supported. However, on the AWS side, you can find the dependencies here: Virtual Routes: Virtual Gateway Rotues: For both resources, under match configuration, port match is optional for a single listener but required for multiple listeners. |
I think I see now. Target Port is a required attribute when the target Virtual Node has multiple listeners, but is not yet in the schema. 🤔 OK, let me see if I can add Target Port as well. |
@SW386 I think that should do it for adding target ports. Could you have a look and confirm everything looks to be in order? |
This looks right to me! |
Seems another PR #27799 was merged instead. Closing. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Add multiple listeners to App Mesh in order to support the changes made generally available on Aug 17, 2022.
Relations
Closes #26380
References
https://aws.amazon.com/about-aws/whats-new/2022/08/aws-app-mesh-support-multiple-listeners/
Output from Acceptance Testing